Dynamic management of restful endpoints

ABSTRACT

Embodiments of the present invention disclose methods, systems, and program products for dynamically managing RESTful endpoints. In one embodiment, an application server provides dynamic management of RESTful endpoint, including the ability to re-use the same resource information for multiple endpoints across multiple routers, allowing for applications aliases or sharing routing capability between applications. Yet other embodiments of the present invention can provide a high availability application server system and/or failover support for routers and resources, as well as the ability to remotely add new containers and resources to the application server.

STATEMENT ON PRIOR DISCLOSURES BY AN INVENTOR

The following disclosure(s) are submitted under 35 U.S.C. 102(b)(1)(A)as prior disclosures by, or on behalf of, a sole inventor of the presentapplication or a joint inventor of the present application:

-   (i) “New in V8.5.5.Next Alpha (February update)”, Peters, Eric, Feb.    28, 2014, available at    https://developer.ibm.com/wasdev/docs/new-in-v8-5-5-next-alpha/.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of applicationserver software, and more particularly to dynamic management ofendpoints within application server software that comply withrepresentational state transfer protocol.

Representational state transfer (REST) is an architectural styleconsisting of a coordinated set of architectural constraints applied tocomponents, connectors, and data elements, within a distributedhypermedia system. Environments and endpoints that comply with therestraints of the REST abstraction are called “RESTful” environments andendpoints. REST includes several formal architectural constraintsincluding (i) a uniform interface separating clients from servers, and(ii) stateless protocol (i.e., each request from any client contains allthe information necessary to service the request). A RESTful endpoint isa connection point that manages access to one or more resources (i.e., asource of information that can be addressed using a uniform resourceidentifier (URI), such as a URL). RESTful endpoints exchangerepresentations of resources to which they address. A representation isa document containing data provided by the resource, includingassociated metadata. When a resource identified by the URI is accessibleby one or more clients, the endpoint is said to be “exposed.” A commonapproach to exposing RESTful endpoints is through static applications,such as enterprise archive (EAR) files or web application archive (WAR)files, where the endpoints are pre-defined during the compilation of thecode.

The World Wide Web evolved from a system of linked static hypertextdocuments to a system of linked pages that can include dynamic updatesof webpages using web applications and scripting languages, such asJavaScript®, and mark up languages, such as XML®. Web applicationservers, or application servers, efficiently execute procedures (e.g.,programs, routines, and scripts) for supporting the web applicationsthat the web application server supports.

SUMMARY

Embodiments of the present invention provide methods, systems, andprogram products for dynamically managing RESTful endpoints. Accordingto one aspect of the present invention, a method is provided comprising:receiving, by one or more computer processors, a REST request using aproxy, wherein the proxy is a first modular application component thatreceives REST requests associated with a context root; determining, byone or more computer processors, a third modular application componentfrom a plurality of modular application components for processing theREST request using a second modular application component, wherein thesecond modular application component selects the third modularapplication component for processing the REST request using one or moreheuristic matching techniques; and processing, by one or more computerprocessors, the REST request using at least the third modularapplication component.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a RESTfulclient-server environment, in accordance with an embodiment of thepresent invention;

FIG. 2 is a flowchart depicting operational steps for handling a RESTrequest, on a computer server within the environment of FIG. 1, inaccordance with an embodiment of the present invention;

FIG. 3 is a functional block diagram illustrating a RESTful applicationserver, in accordance with an embodiment of the present invention; and

FIG. 4 depicts a block diagram of components of the computer serverexecuting the application server, in accordance with an embodiment ofthe present invention.

DETAILED DESCRIPTION

Embodiments of the present invention recognize that typical approachesfor exposing RESTful endpoints (e.g., through EAR or WAR file upload)pre-define the endpoints at the time of code compilation. These methodsof exposing the endpoints do not allow for dynamic management of theendpoints. Dynamic, in the context of exposing RESTful endpoints, meansthat endpoints may be added, removed, and/or modified without (i)stopping and restarting the application server that is executing anendpoint application or (ii) recompiling the application server or anyof the part thereof. Embodiments of the present invention disclose anapplication server that provides dynamic management of RESTfulendpoints. Some embodiments of the present invention further provide theability to re-use the same resource information for multiple endpointsacross multiple routers, allowing for applications aliases or sharingrouting capability between applications, which is particularly useful inenterprise computing environments. Yet other embodiments of the presentinvention can provide a high availability application server systemand/or failover support for routers and resources. Further embodimentsof the present invention provide the ability to remotely add newcontainers and resources to the application server.

Embodiments of the present invention will now be discussed with respectto the several Figures. FIG. 1 is a functional block diagramillustrating a RESTful client-server environment (“environment”),generally designated 100, in accordance with an embodiment of thepresent invention. Environment 100 includes client system 102 andcomputer server 104 connected over network 118. Network 118 can be, forexample, a local area network (LAN), a wide area network (WAN), such asthe Internet, a dedicated short range communications network, or anycombination thereof, and may include wired, wireless, fiber optic, orany other connection known in the art. In general, the communicationnetwork can be any combination of connections and protocols that willsupport communication between client system 102 and computer server 104.

Client system 102 can be a desktop computer, a laptop computer, a tabletcomputer, a specialized computer server, a smartphone, or any othercomputer system known in the art. In certain embodiments, client system102 represents a computer system utilizing clustered computers andcomponents that act as a single pool of seamless resources when accessedthrough network 118, as is common in data centers and with cloudcomputing applications. In general, client system 102 is representativeof any programmable electronic device, or combination of programmableelectronic devices, capable of executing machine-readable programinstructions and communicating with other computing devices via anetwork.

Computer server 104 can be a desktop computer, a laptop computer, atablet computer, a specialized computer server, a smartphone, or anyother computer system known in the art. In certain embodiments, computerserver 104 represents a computer system utilizing clustered computersand components that act as a single pool of seamless resources whenaccessed through network 118, as is common in data centers and withcloud computing applications. In general, computer system 104 isrepresentative of any programmable electronic device, or combination ofprogrammable electronic devices, capable of executing machine-readableprogram instructions and communicating with other computing devices viaa network. Exemplary components of computer system 104 are described ingreater detail with regard to FIG. 4. Computer server 104 includesapplication server 106. Application server 106 includes the followingmodular application components: REST proxy 108, REST handler container110, REST handlers 112 and 114, and REST helper 116.

Application server 106 is a software development and application runtimeenvironment. Application server 106 provides software abstractions forservices that are intended to be used by a large number of clients withaccess to computer server 104. In various embodiments of the presentinvention, the services of application server 106 can include one ormore REST proxies, such as REST proxy 108, one or more REST handlercontainers, such as REST handler container 110, one or more RESThandlers, such as REST handlers 112 and 114, and one or more RESThelpers, such as REST helper 116. Application server 110 can beimplemented using any dynamic programming framework with capability toallow a software developer to add, remove, or alter REST proxies, RESThandler containers, REST handlers, and/or REST helpers without requiringapplication server 106 to restart and/or without requiring recompilationof the program code that defines application server 106 and itscomponent parts (i.e., REST proxy 108, REST handler container 110, RESThandlers 112 and 114, and REST helper 116). For example, applicationserver 106 can utilize modular frameworks such as Open Source GatewayInitiative (OSGi™), JRebel®, Service Oriented Framework (SOF), OSGI4Cpp,or Portable Components (POCO) library, or any other modular frameworkthat allows a software system to be separated into several smallercomponents which communicate via clearly defined interfaces.

REST proxy 108 is a layer of web application code embodied as a modularapplication component that is associated with a specific context root. Acontext root is a name that maps to a RESTful endpoint. REST requeststransmitted by client system 102 to server computer 104 are associatedwith specified context roots (e.g., a URL). REST proxy 108 listens forrequests associated with a specific context root, and delegates incomingrequests to REST handler container 110 for processing of incoming RESTrequests. REST proxy 108 can be, for example, a servlet or an HTTPtransport listener designed to listen to a specified context root andpass incoming REST requests to REST handler container 110. In variousembodiments of the present invention, application server 106 can includemultiple REST proxies, each of which listens to a different contextroot. By defining multiple REST proxies and other servlets, differentapplication layers can use and share the same REST handler container, aswell as the same REST handlers and REST helpers. For example, a firstservlet may be configured to work with Java Management Extensions (JMX),while a second servlet may be configured to work with Legacy Javaapplications, but both servlets may pass requests to the same RESThandler container for processing.

REST handler container 110 is a modular application component capable ofreceiving incoming REST requests from REST proxy 108, determining one ormore REST handlers and/or REST helpers best suited to handle in theincoming requests, for example, through heuristic analysis of the RESTrequests, and designating the incoming REST requests to the one or moreREST handlers and/or REST helpers. REST handler container 110 managesthe life cycle of REST handlers 112 and 114 and REST helper 116, forexample, by dictating when to call the REST handlers and REST helpersand when to remove them. REST handler container 110 maintains a list ofall of the available REST handlers and REST helpers and an internalmapping mechanism that controls which REST handlers/REST helperscontribute to which REST proxies. REST handler container 110 can beimplemented using any dynamic programming framework with capability toallow a software developer to add, remove, or alter REST proxies, RESThandler containers, REST handlers, and/or REST helpers without requiringapplication server 106 to restart and/or without requiring recompilationof the program code that defines application server 106 and itscomponent parts.

In various embodiments, multiple REST handler containers may existwithin a single instance of application server 106. In such embodiments,application server 106 contains a primary REST handler container (i.e.,REST handler container 110) and one or more background REST handlercontainers that can sync with the primary REST handler container atregular intervals. If the primary REST handler container fails or isdeactivated, one of the background REST handler containers can declareitself as the new primary REST handler container and the applicationserver will continue to function normally. Accordingly, embodiments ofthe present invention provide a high availability application serverenvironment. In other embodiments, the multiple REST handler containersmay provide internal load balancing functions for application server106. For example, if application server 106 receives a REST request thatcontains code blocks that must be synchronized (i.e., executed by asingle thread at a time), then the primary REST handler container candelegate waiting threads to one or more of the background REST handlercontainers so that parallel processing can occur and improve thefunctionality of application server 106.

REST handlers 112 and 114 are modular application components thatprovide the core logic for a given REST endpoint. REST handlers 112 and114 can be implemented using any dynamic programming framework withcapability to allow a software developer to add, remove, or alter RESThandlers 112 and 114 without requiring application server 106 torestart, and/or without requiring recompilation of the program code thatdefines application server 106 and its component parts. REST handlers112 and 114 each correspond to a RESTful endpoint, for example, aspecific URI or URL. By having multiple REST handlers and REST helpersshare a common REST handler container, each REST helper can contributeto more than just a single application, which reduces code duplicationand allows for a platform in which each REST handler performs a specifictype of logic and all applications can take advantage of thespecialization. Because REST handlers 112 and 114 are implemented asmodular application components, they may be added, removed, or modifiedremotely using existing commands within the modular framework (e.g.,OSGi™).

REST helper 116 is a modular application component that provides aspecific functionality which may be useful across multiple RESTfulendpoints. For example, in one embodiment, a REST helper in anapplication server may handle adding HTTP headers to a request responseto facilitate cross-origin resource sharing (CORS). In anotherembodiment, a REST helper can control routing within a cluster ofcomputers. REST helper 116 can be implemented using any dynamicprogramming framework with capability to allow a software developer toadd, remove, or alter REST helper 116 without requiring applicationserver 106 to restart, and/or without requiring recompilation of theprogram code that defines application server 106 and/or its componentparts.

In one embodiment, REST helper 116 enables a software developer toremotely deploy new REST handlers and/or REST helpers. In thisembodiment, application server 106 includes a remote REST proxyconfigured to receive new REST handler and/or REST helper deployments ata specified context root. For example, a software developer can submit astandard PUT command to the remote REST proxy with a payload consistingof a binary representation (stub) of the new REST handler or REST helperin the same language that the application server framework isconstructed in (e.g., OSGi™). The remote REST proxy instructs RESThandler container 110 to REST helper 116. In this embodiment, RESThelper 116 comprises a compiler for processing binary stubs anddeploying new REST handlers or REST helpers within the framework.

FIG. 2 is a flowchart depicting operational steps for handling a RESTrequest, on a computer server within the environment of FIG. 1, inaccordance with an exemplary embodiment of the present invention.

In step 202, application server 106 receives a REST request using RESTproxy 108. In the exemplary embodiment of FIG. 2, client 102 transmits aREST request to server computer 104 via network 118. As discussed withrespect to FIG. 1, REST proxy 108 is a modular construct that receivesREST requests associated with a specific context root. For example, RESTproxy 108 may be a servlet or HTTP transfer listener. REST proxy 108provides a lightweight (relative to a complete application server)framework for receiving REST requests associated with specific contextroots. In various embodiments of the present invention, REST proxy 108provides only a front layer construct for receiving REST requests, andthen passes the requests to REST handler container 110.

In step 204, application server 106 determines a REST handler or a RESThelper to perform a task associated with the REST request using RESThandler container 110. As discussed above, REST handler container is amodular container that manages the life cycles of one or more RESThandlers and/or REST helpers. In the exemplary embodiment of FIG. 2,REST handler container 110 determines which REST handler or REST helpershould handle a task associated with the received REST request using oneor more heuristic matching mechanisms such as, path matching, servicerank, routing requirements, or custom security. Path matching may, forexample, include the matching of information included in the URL of theREST request with information associated with a REST handler indicatingthe type of REST requests that the REST handler can process. Theinformation associated with the REST handlers that indicates specificfunctionality of the REST handlers may be included as part of the RESThandler container.

In step 206, application server 106 assigns the task to the determinedREST handler or REST helper. In the exemplary embodiment of FIG. 2, RESThandler container 110 passes the REST request to a REST handler (e.g.,REST handler 112) which performs the core logic for processing the RESTrequest. For example, if an incoming REST request matches a specificpath that is handled by a REST handler, as determined by REST handlercontainer 110, the REST handler container 110 designates the RESTrequest to the determined REST handler, which performs the tasksassociated with the REST request and returns any information required toclient 102.

FIG. 3 is a functional block diagram illustrating a bundled RESTfulapplication server, in accordance with an illustrative embodiment of thepresent invention. FIG. 3 provides a visual representation of modularREST handlers and REST helpers that enable embodiments of the presentinvention to provide users with dynamic management capabilities of thevarious RESTful endpoints associated with application server 302.

FIG. 3 provides an alternative embodiment of application server 106 fromthe exemplary embodiment of FIG. 1. In the illustrative embodiment ofFIG. 3, application server 302 includes REST proxy 304 and REST handlercontainer 306. REST proxy 304 and REST handler container 306 function ina similar way to REST proxy 108 and REST handler container 110 inFIG. 1. In the illustrative embodiment of FIG. 3, the various RESThandlers and REST helpers are bundled together using a modularprogramming framework, such as OSGi™. In the illustrative embodiment ofFIG. 3, REST handlers 310 and 312 and REST helper 314 are bundledtogether into bundle 308. Similarly, REST handlers 318 and 320 and RESThelper 322 are bundled together into bundle 316. In certain embodiments,REST handlers and REST helpers are bundled together based on similarfunctionality. Additionally, bundling enables software developersresponsible for maintaining the application server to easily add,remove, or modify the components of the application server usingpre-existing commands for the modular framework utilized in constructingthe application server environment.

FIG. 4 depicts a block diagram of components of computer server inaccordance with an illustrative embodiment of the present invention. Itshould be appreciated that FIG. 4 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Computer server 104 includes communications fabric 402, which providescommunications between computer processor(s) 404, memory 406, persistentstorage 408, communications unit 412, and input/output (I/O)interface(s) 414. Communications fabric 402 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as microprocessors, communications and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric402 can be implemented with one or more buses.

Memory 406 and persistent storage 408 are computer-readable storagemedia. In this embodiment, memory 406 includes random access memory(RAM) 414 and cache memory 416. In general, memory 406 can include anysuitable volatile or non-volatile computer-readable storage media.

Application server 106 is stored in persistent storage 408 for accessand/or execution by one or more of the respective computer processors404 via one or more memories of memory 406. In this embodiment,persistent storage 408 includes a magnetic hard disk drive.Alternatively, or in addition to a magnetic hard disk drive, persistentstorage 408 can include a solid state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer-readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 408 may also be removable. Forexample, a removable hard drive may be used for persistent storage 408.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer-readable storage medium that is also part of persistent storage408.

Communications unit 412, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 412 includes one or more network interface cards.Communications unit 412 may provide communications through the use ofeither or both physical and wireless communications links. Applicationserver 106 may be downloaded to persistent storage 408 throughcommunications unit 412.

I/O interface(s) 414 allows for input and output of data with otherdevices that may be connected to computer server 104. For example, I/Ointerface 414 may provide a connection to external devices 420 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 420 can also include portable computer-readablestorage media such as, for example, thumb drives, portable optical ormagnetic disks, and memory cards. Software and data used to practiceembodiments of the present invention, e.g., application server 106, canbe stored on such portable computer-readable storage media and can beloaded onto persistent storage 408 via I/O interface(s) 414. I/Ointerface(s) 414 also connect to a display 422.

Display 422 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

1-7. (canceled)
 8. A computer program product for dynamically managingRESTful endpoints, the computer program product comprising: one or morecomputer-readable storage media and program instructions stored on theone or more computer-readable storage media, the program instructionscomprising: program instructions to receive a REST request using aproxy, wherein the proxy is a first modular application component thatreceives REST requests associated with a context root; programinstructions to determine a third modular application component from aplurality of modular application components for processing the RESTrequest using a second modular application component, wherein the secondmodular application component selects the third modular applicationcomponent for processing the REST request using one or more heuristicmatching techniques; and program instructions to process the RESTrequest using at least the third modular application component.
 9. Thecomputer program product of claim 8, wherein the one or more heuristicmatching techniques comprise at least one of path matching, servicerank, routing requirements, or custom security.
 10. The computer programproduct of claim 8, wherein the REST request comprises a binaryrepresentation of a fourth modular application component, and the thirdmodular application component comprises a binary compiler for convertingthe REST request into the fourth modular application component capableof processing REST requests.
 11. The computer program product of claim10, wherein the program instructions stored on the one or morecomputer-readable storage media further comprise: program instructionsto create the fourth modular application component, wherein the fourthmodular application component can process one or more REST requests. 12.The computer program product of claim 8, wherein one or more of theplurality of modular application components are grouped into one or morebundles, wherein the one or more bundles may be modified withoutrecompiling the plurality of modular application components.
 13. Thecomputer program product of claim 8, wherein the program instructionsstored on the one or more computer-readable storage media furthercomprise: program instructions to generate one or more redundantinstances of the second modular application component.
 14. The computerprogram product of claim 13, wherein the program instructions stored onthe one or more computer-readable storage media further comprise:program instructions to determine that the second modular applicationcomponent has become unavailable; and program instructions to,responsive to determining that the second modular application componenthas become unavailable, replace the second modular application componentwith at least one of the one or more redundant instances of the secondmodular application component.
 15. A computer system for dynamicallymanaging RESTful endpoints, the computer system comprising: one or morecomputer processors; one or more computer-readable storage media;program instructions stored on the computer-readable storage media forexecution by at least one of the one or more processors, the programinstructions comprising: program instructions to receive a REST requestusing a proxy, wherein the proxy is a first modular applicationcomponent that receives REST requests associated with a context root;program instructions to determine a third modular application componentfrom a plurality of modular application components for processing theREST request using a second modular application component, wherein thesecond modular application component selects the third modularapplication component for processing the REST request using one or moreheuristic matching techniques; and program instructions to process theREST request using at least the third modular application component. 16.The system of claim 15, wherein the one or more heuristic matchingtechniques comprise at least one of path matching, service rank, routingrequirements, or custom security.
 17. The system of claim 15, whereinthe REST request comprises a binary representation of a fourth modularapplication component, and the third modular application componentcomprises a binary compiler for converting the REST request into thefourth modular application component capable of processing RESTrequests.
 18. The system of claim 17, wherein the program instructionsstored on the computer-readable storage media further comprise: programinstructions to create the fourth modular application component, whereinthe fourth modular application component can process one or more RESTrequests.
 19. The system of claim 15, wherein one or more of theplurality of modular application components are grouped into one or morebundles, wherein the one or more bundles may be modified withoutrecompiling the plurality of modular application components.
 20. Thesystem of claim 15, wherein the program instructions stored on thecomputer-readable storage media further comprise: program instructionsto generate one or more redundant instances of the second modularapplication component; program instructions to determine that the secondmodular application component has become unavailable; and programinstructions to, responsive to determining that the second modularapplication component has become unavailable, replace the second modularapplication component with at least one of the one or more redundantinstances of the second modular application component.